Method for determining trigger state, terminal device, and network device

ABSTRACT

Provided in embodiments of the present application are a method and apparatus for determining trigger state, a terminal device, and a communication device; the method comprises: a terminal device receiving first configuration information sent by a network device, the first configuration information comprising configuration information of at least one trigger state; the terminal device receiving first control information sent by the network device, the first control information comprising a first information domain; the terminal device determining a first trigger state identifier on the basis of the value of the first information domain, and determining a corresponding first trigger state in the first configuration information on the basis of the first trigger state identifier; or, the terminal device determining a first trigger state at a target position in the first configuration information on the basis of the value of the first information domain.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation application of U.S. patentapplication Ser. No. 17/003,849, filed Aug. 26, 2020, which is acontinuation of International application No. PCT/CN2018/108003, filedon Sep. 27, 2018 and entitled “METHOD AND APPARATUS FOR DETERMININGTRIGGER STATE, TERMINAL, AND NETWORK DEVICE”, the disclosures of whichare hereby incorporated by reference in their entirety.

TECHNICAL FIELD

The disclosure relates to the technical field of mobile communications,and in particular to a method for determining a triggering state, aterminal device, and a network device.

BACKGROUND

In a new radio (NR) system, reporting operation of a terminal deviceinclude periodic reporting, aperiodic (AP) reporting and semi-persistent(SP) reporting. both the AP reporting and the SP reporting can betriggered by downlink control information (DCI), and reported content istransmitted through a physical uplink shared channel (PUSCH).

In order to complete the DCI-based reporting trigger mechanism asdescribed above, the following are designed in the NR system: 1) achannel state information (CSI) triggering state list, and 2) a specificfield in the DCI, called a CSI request field. In order to triggerreporting, a correspondence relation from a triggering state to acodepoint of a CSI request field needs to be determined, and how todetermine the correspondence relation is a problem to be solved.

DETAILED DESCRIPTION OF THE DRAWINGS

The accompanying drawings are described here to provide furtherunderstanding of the disclosure and constitute part of the disclosure.Exemplary embodiments of the disclosure and description thereof are forthe purpose of explanation, and do not for inappropriate limitation tothe disclosure. In the drawings:

FIG. 1 illustrates a schematic diagram of a communication systemarchitecture according to some embodiments of the disclosure.

FIG. 2 illustrates a first schematic flow chart of a method fordetermining a triggering state according to some embodiments of thedisclosure.

FIG. 3 illustrates a second schematic flow chart of a method fordetermining a triggering state according to some embodiments of thedisclosure.

FIG. 4 illustrates a first schematic diagram of structural compositionof a device for determining a triggering state according to someembodiments of the disclosure.

FIG. 5 illustrates a second schematic diagram of structural compositionof a device for determining a triggering state according to someembodiments of the disclosure.

FIG. 6 illustrates a schematic structural diagram of a communicationdevice according to some embodiments of the disclosure.

FIG. 7 illustrates a schematic structural diagram of a chip according tosome embodiments of the disclosure.

FIG. 8 illustrates a schematic block diagram of a communication systemaccording to some embodiments of the disclosure.

DETAILED DESCRIPTION

The technical solutions according to embodiments of the disclosure willbe described hereinbelow in conjunction with the accompanying drawingsin the embodiments of the disclosure. Apparently, the describedembodiments are merely some of the embodiments rather than allembodiments of the disclosure. Based on the embodiments of thedisclosure, all other embodiments obtained by those of ordinary skill inthe art without making any inventive effort shall fall within theprotection scope of the disclosure.

The technical solutions according to embodiments of the disclosure maybe applied to various communication systems, for example, a globalsystem for mobile communication (GSM) system, a code division multipleaccess (CDMA) system, a wideband code division multiple access (WCDMA)system, a general packet ratio service (GPRS) system, a long termevolution (LTE) system, an LTE frequency division duplex (FDD) system,an LTE time division duple (TDD) system, and a universal mobiletelecommunication system (UMTS), a worldwide interoperability formicrowave access (WiMAX) communication system or a 5G system.

Exemplarily, a communication system 100 to which the embodiments of thedisclosure are applied is illustrated in FIG. 1 . The communicationsystem 100 may include a network device 110, and the network device 110may be a device communicating with a terminal device 120 (or called acommunication terminal or terminal). The network device 110 can providecommunication coverage for a specific geographical area, and cancommunicate with a terminal device within the covered area. The networkdevice 110 may be a base transceiver station (BTS) in a GSM system orCDMA system, a NodeB (NB) in a WCDMA system, an evolutional NodeB (eNBor eNodeB) in an LTE system, or a radio controller in a cloud radioaccess network (CRAN). The network device may also be a mobile switchingcenter, a relay station, an access point, a vehicle-mounted device, awearable device, a hub, a switch, a bridge, a router, a network-sidedevice in a 5G network, a network device in a future evolved public landmobile network (PLMN) or the like.

The communication system 100 further includes at least one terminaldevice 120 within the coverage of the network device 110. “Terminaldevice” as used here includes but is not limited to being connected viaa wired line, for example, via a public switched telephone network(PSTN), a digital subscriber line (DSL), a digital cable, or a directcable connection; and/or via another data connection/network; and/or viaa wireless interface, for example for a cellular network, a wirelesslocal area network (WLAN), a digital telephone network such as a DVB-Hnetwork, a satellite network, or an AM-FM broadcast transmitter; and/orvia a device of another terminal device configured to receive/send acommunication signal; and/or via an Internet of things (IoT) device.

A terminal device configured to communicate via a wireless interface maybe called a “wireless communication terminal”, a “wireless terminal” ora “mobile terminal”. Examples of a mobile terminal include but are notlimited to: a satellite phone or a cell phone; a personal communicationsystem (PCS) terminal which can combine a cellular radio phone with dataprocessing, faxing and data communication capabilities; a personaldigital assistant (PDA) that may include a radio phone, a pager,Internet/intranet access, a Web browser, a notebook, a calendar and/or aglobal positioning system (GPS) receiver; a conventional laptop and/orhandheld receiver; or other electronic devices including a radiotelephone transceiver.

The terminal device may be an access terminal, a user equipment (UE), asubscriber unit, a user station, a mobile station, a remote station, aremote terminal, a mobile device, a user terminal, a wirelesscommunication device, a user agent or a user device. The access terminalmay be a cell phone, a cordless phone, a session initiation protocol(SIP) phone, a wireless local loop (WLL) station, a personal digitalassistant (PDA), a hand-held device with a wireless communicationfunction, a computing device or other processing devices connected to awireless modem, a vehicle-mounted device, a wearable device, a terminaldevice in a 5G network, a terminal device in a future evolved PLMN orthe like.

Terminal devices 120 may communicate with each other through device todevice (D2D) communication.

A 5G system or a 5G network may also be called a new radio (NR) systemor an NR network.

FIG. 1 illustrates a network device and two terminal devices in anexemplary way. The communication system 100 may include multiple networkdevices, and there may be another number of terminal devices within thecoverage of each of the terminal devices, which will not be limited inembodiments of the disclosure.

The communication system 100 may further include other network entitiessuch as a network controller, and a mobility management entity, whichwill not be limited in embodiments of the disclosure.

It is to be understood that a device with a communication function in anetwork/system in embodiments of the disclosure may be called acommunication device. With the communication system 100 illustrated inFIG. 1 as an example, the communication devices may include a networkdevice 110 and a terminal device 120, each having a communicationfunction. The network device 110 and the terminal device 120 may be thespecific devices as described above, which will not be described here.The communication devices may further include other devices in thecommunication system 100, for example, other network entities such as anetwork controller, and a mobility management entity, which will not belimited in embodiments of the disclosure.

It is to be understood that terms “system” and “network” used here areoften used interchangeably. The term “and/or” is used here to describeassociation relations between associated objects, and three relationsmay be indicated. For example, A and/or B may indicate three situations:A exists alone, both A and B exist at the same time, and B exists alone.In addition, the character “/” here generally indicates an “or” relationbetween associated objects before and after the character.

A method and device for determining a triggering state, a terminaldevice, and a network device are provided in embodiments of thedisclosure.

A method for determining a triggering state provided in embodiments ofthe disclosure includes: receiving, by a terminal device, firstconfiguration information from a network device, wherein the firstconfiguration information includes configuration information of at leastone triggering state; and receiving, by the terminal device, firstcontrol information from the network device, wherein the first controlinformation includes a first information field. The method furtherincludes: determining, by the terminal device, based on a codepoint ofthe first information field, a first triggering state identification(ID), and determining, based on the first triggering state ID, acorresponding first triggering state in the first configurationinformation; or determining, by the terminal device, based on thecodepoint of the first information field, the first triggering state ata target position in the first configuration information.

A method for determining a triggering state provided in embodiments ofthe disclosure includes: sending, by a network device, firstconfiguration information to a terminal device, wherein the firstconfiguration information includes configuration information of at leastone triggering state; and sending, by the network device, first controlinformation to the terminal device, wherein the first controlinformation includes a first information field. A codepoint of the firstinformation field is used for the terminal device to determine a firsttriggering state identification (ID), and to determine, based on thefirst triggering state ID, a corresponding first triggering state in thefirst configuration information; or the codepoint of the firstinformation field is used for the terminal device to determine the firsttriggering state at a target position in the first configurationinformation.

A device for determining a triggering state includes: a first receivingunit, configured to receive first configuration information from anetwork device, wherein the first configuration information includesconfiguration information of at least one triggering state; a secondreceiving unit, configured to receive first control information from thenetwork device, wherein the first control information includes a firstinformation field; and a determination unit, configured to determine,based on a codepoint of the first information field, a first triggeringstate identification (ID), and determine, based on the first triggeringstate ID, a corresponding first triggering state in the firstconfiguration information; or configured to determine, based on thecodepoint of the first information field, the first triggering state ata target position in the first configuration information.

A device for determining a triggering state includes: a first sendingunit, configured to send first configuration information to a terminaldevice, wherein the first configuration information includesconfiguration information of at least one triggering state; and a secondsending unit, configured to send first control information to theterminal device, wherein the first control information includes a firstinformation field. A codepoint of the first information field is usedfor the terminal device to determine a first triggering stateidentification (ID), and to determine, based on the first triggeringstate ID, a corresponding first triggering state in the firstconfiguration information; or the codepoint of the first informationfield is used for the terminal device to determine the first triggeringstate at a target position in the first configuration information.

A terminal device provided in embodiments of the disclosure includes aprocessor and a memory for storing a computer program. The processor isconfigured to call and run the computer program stored in the memory, toperform the above method for determining a triggering state.

A network device provided in embodiments of the disclosure includes aprocessor and a memory for storing a computer program. The processor isconfigured to call and run the computer program stored in the memory, toperform the above method for determining a triggering state.

A chip for implementing the above method for determining a triggeringstate is provided in embodiments of the disclosure. In particular, thechip includes a processor configured to call and run a computer programfrom a memory, to enable a device installed with the chip to perform theabove method for determining a triggering state.

Provided in embodiments of the disclosure is a computer-readable storagemedium for storing a computer program which enables a computer toperform the above method for determining a triggering state.

Provided in embodiments of the disclosure is a computer program productincluding computer program instructions which enable a computer toperform the above method for determining a triggering state.

Provided in embodiments of the disclosure is a computer program which,when running on a computer, enables the computer to perform the abovemethod for determining a triggering state.

In the technical solutions above, a triggering state identification (ID)is defined for each triggering state, and a terminal device candetermine a corresponding triggering state according to a correspondencerelation between a codepoint of a CSI request field in DCI and atriggering state ID, so as to realize a reporting operationcorresponding to the triggering state. The terminal device can alsodirectly determine the corresponding triggering state according to acorrespondence relation between the codepoint of the CSI request fieldin DCI and a position of the triggering state, so as to realize areporting operation corresponding to the triggering state. Due to thecorrespondence relation between the codepoint of the CSI request fieldand the triggering state ID or the position of the triggering state, anetwork side can trigger a reporting operation of the terminal device byusing the DCI.

To better understand the technical solutions according to embodiments ofthe disclosure, related techniques involved in the embodiments of thedisclosure are explained below.

1. CSI Triggering State List

There are two types of CSI triggering state lists: a CSI triggeringstate list corresponding to aperiodic (AP) reporting (called aCSI-AperiodicTriggerStateList), and a CSI triggering state listcorresponding to semi-persistent (SP) reporting (called aCSI-SemiPersistentOnPUSCH-TriggerStateList).

In the definition of the CSI-AperiodicTriggerStateList, configurationinformation for each aperiodic triggering state is defined. In thedefinition of the CSI-SemiPersistentOnPUSCH-TriggerStateList,configuration information for each semi-persistent triggering state isdefined. Here, the configuration information of each triggering statemay include but is not limited to: what information to measure, whatinformation to report, a way of information reporting, etc.

2. CSI Request Field

The CSI request field is a specific information field in DCI. Acodepoint of the CSI request field is a value of the CSI request field.For example, if the CSI request field consists of two bits, a codepointof the CSI request field may be 00, 01, 10, or 11.

In an NR system, AP reporting and SP reporting may be triggered by DCI.In particular, a correspondence relation between codepoints of a CSIrequest field in the DCI and triggering states needs to be determined.That is to say, after detecting a codepoint of the CSI request field, auser equipment (UE) needs to know which triggering state the codepointcorresponds to.

3. A Relation Between Triggering States and Codepoints of the CSIRequest Field

For aperiodic reporting, all-zero codepoints correspond to no aperiodicreporting. Therefore, a starting codepoint corresponding to a triggeringstate is 1.

For semi-persistent reporting, a starting codepoint corresponding to atriggering state is 0.

In order to realize correspondence (also called mapping) betweencodepoints and triggering states, a particular mapping scheme isprovided in the embodiments of the disclosure.

FIG. 2 illustrates a first schematic flow chart of a method fordetermining a triggering state according to some embodiments of thedisclosure. As illustrated in FIG. 2 , the method for determining atriggering state includes actions 201, 202 and 203.

In action 201, a terminal device receives first configurationinformation from a network device. The first configuration informationincludes configuration information of at least one triggering state.

In embodiments of the disclosure, the terminal device may be any devicecapable of communicating with a network, such as a mobile phone, atablet, a vehicle-mounted terminal device and a notebook.

In embodiments of the disclosure, the network device is a base station,for example a gNB in a 5G network, and an eNB in a 4G network.

In embodiments of the disclosure, the first configuration information istransmitted via high-level signalling. The high-level signalling isradio resource control (RRC) signalling.

In embodiments of the disclosure, the first configuration informationincludes configuration information of at least one triggering state.Further, the first configuration information may be RRC signalling forconfiguring a CSI-AperiodicTriggerStateList, or an RRC signalling forconfiguring a CSI-SemiPersistentOnPUSCH-TriggerStateList.

The first configuration information includes configuration informationof one or more triggering states. Generally, the first configurationinformation includes configuration information of multiple triggeringstates. The configuration information of each triggering state mayinclude but is not limited to: what information to measure, whatinformation to report, a way of information reporting, etc.

In action 202, the terminal device receives first control informationfrom the network device. The first control information includes a firstinformation field.

In a specific implementation, the first control information may be DCI.The first information field in the first control information may becalled a CSI request field. Further, a value of the first informationfield is a codepoint of the CSI request field. For example, the firstinformation field includes 3 bits, and a codepoint of the firstinformation field may be: 000, 001, 010, 011, 100, 101, 110, or 111.

In action 203, the terminal device determines, based on a codepoint ofthe first information field, a first triggering state identification(ID), and determines, based on the first triggering state ID, acorresponding first triggering state in the first configurationinformation; or the terminal device determines, based on the codepointof the first information field, the first triggering state at a targetposition in the first configuration information.

In embodiments of the disclosure, a codepoint of the first informationfield corresponds to a triggering state in the first configurationinformation. The correspondence relation may be determined in one of thefollowing approaches.

Approach 1: configuration information of each of the at least onetriggering state in the first configuration information includes asecond information field. The second information field indicates atriggering state ID of the triggering state.

In particular, when the first configuration information is configurationinformation for aperiodic reporting, configuration information of eachaperiodic triggering state includes the second information field. Thesecond information field indicates a triggering state ID of theaperiodic triggering state. When the first configuration information isconfiguration information for semi-persistent reporting, configurationinformation of each semi-persistent triggering state includes the secondinformation field. The second information field indicates a triggeringstate ID of the semi-consistent triggering state.

In a specific implementation, a triggering state ID (called a state ID)field (i.e., the second information field) may be added to RRCsignalling carrying the first configuration information. Theimplementation of the state ID field is described in combination withfirst configuration information for aperiodic reporting and firstconfiguration information for semi-persistent reporting respectively.

Please see table 1 in the below. Table 1 provides information of aCSI-AperiodicTriggerStateList, in which a state ID field labelled withan underline is added. It is to be noted that, in the configurationinformation of each CSI-AperiodicTriggerState, a corresponding state IDfield is added, so as to indicate the state ID corresponding to thetriggering state by the state ID field. The value of the state ID is ofa type of numeric.

TABLE 1 -- ASN1START -- TAG-CSI-APERIODICTRIGGERSTATELIST-STARTCSI-AperiodicTriggerStateList ::= SEQUENCE (SIZE (1..maxNrOfCSI-AperiodicTriggers)) OF CSI-AperiodicTriggerStateCSI-AperiodicTriggerState ::= SEQUENCE{  stateID  numeric associatedReportConfigInfoList SEQUENCE(SIZE(1..maxNrofReportConfigPerAperiodicTrigger)) OF CSI-AssociatedReportConfigInfo,  . . . } CSI-AssociatedReportConfigInfo ::=SEQUENCE {  reportConfigId  CSI-ReportConfigId,  resourcesForChannel CHOICE {   nzp-CSI-RS    SEQUENCE {    resourceSet     INTEGER(1..maxNrofNZP-CSI- RS-ResourceSetsPerConfig),    qcl-info     SEQUENCE(SIZE(1..maxNrofAP-CSI-RS-ResourcesPerSet)) OF TCI-StateId OPTIONAL --Cond Aperiodic   },   csi-SSB-ResourceSet   INTEGER (1..maxNrofCSI-SSB-ResourceSetsPerConfig)  },  csi-IM-ResourcesForInterference INTEGER(1..maxNrofCSI-IM- ResourceSetsPerConfig) OPTIONAL, -- CondCSI-IM-ForInterference  nzp-CSI-RS-ResourcesForInterference INTEGER(1..maxNrofNZP-CSI-RS- ResourceSetsPerConfig) OPTIONAL, -- CondNZP-CSI-RS-ForInterference  . . . } --TAG-CSI-APERIODICTRIGGERSTATELIST-STOP -- ASN1STOP

Please see table 2 below. Table 2 provides information of aCSI-SemiPersistentOnPUSCH-TriggerStateList, in which a state ID fieldlabelled with an underline is added. It is to be noted that, in theconfiguration information of eachCSI-SemiPersistentOnPUSCH-TriggerState, a corresponding state ID fieldis added, so as to indicate the state ID corresponding to the triggeringstate by the state ID field. The value of the state ID is of a type ofnumeric.

TABLE 2 -- ASN1START --TAG-CSI-SEMIPERSISTENTONPUSCHTRIGGERSTATELIST-STARTCSI-SemiPersistentOnPUSCH-TriggerStateList ::= SEQUENCE(SIZE (1..maxNrOfSemiPersistentPUSCH-Triggers)) OF CSI-SemiPersistentOnPUSCH-TriggerState CSI-SemiPersistentOnPUSCH-TriggerState ::= SEQUENCE { stateID   numeric  associatedReportConfigInfo  CSI-ReportConfigId,  . .. } --TAG-CSI-SEMIPERSISTENTONPUSCHTRIGGERSTATELIST-STOP -- ASN1STOP

By the approach 1, the terminal device can determine, based on acodepoint of the first information field, a first triggering state ID,and determine, based on the first triggering state ID, a correspondingfirst triggering state in the first configuration information.

Approach 2: a position of each of the at least one triggering state inthe first configuration information corresponds to a triggering state IDof the triggering state.

In particular, when the first configuration information is configurationinformation for aperiodic reporting, a position of each aperiodictriggering state in the first configuration information corresponds to atriggering state ID of the aperiodic triggering state. When the firstconfiguration information is configuration information forsemi-persistent reporting, a position of each semi-persistent triggeringstate in the first configuration information corresponds to a triggeringstate ID of the semi-persistent triggering state.

In an implementation, triggering state IDs of triggering states in thefirst configuration information are sorted in an ascending order from afirst position to a last position for the triggering states.

In another implementation, the triggering state IDs of the triggeringstates in the first configuration information are sorted in a descendingorder from the first position to the last position for the triggeringstates.

In a specific implementation, RRC signalling carrying firstconfiguration information may keep unchanged, and a triggering state IDis determined implicitly through a position of a triggering state. Howto determine the triggering state ID implicitly is described incombination with first configuration information for aperiodic reportingand first configuration information for semi-persistent reportingrespectively.

The first configuration information for aperiodic reporting contains alist, i.e., a CSI-AperiodicTriggerStateList, and a state IDcorresponding to a triggering state may be determined according to aposition of the triggering state in the first configuration information(i.e., the position in the RRC signalling). For example, a state IDcorresponding to a first triggering state is 0, and a state IDcorresponding to a second triggering state is 1, and so forth.Alternatively, state IDs are sorted in another order. For example, astate ID corresponding to the last triggering state is 0, and a state IDcorresponding to the last but one triggering state is 1, and so forth.

Similarly, the first configuration information for semi-persistentreporting contains a list, i.e., aCSI-SemiPersistentOnPUSCH-TriggerStateList, and a state ID correspondingto a triggering state may be determined according to a position of thetriggering state in the first configuration information (i.e., theposition in the RRC signalling). For example, a state ID correspondingto a first triggering state is 0, and a state ID corresponding to asecond triggering state is 1, and so forth. Alternatively, state IDs aresorted in another order. For example, a state ID corresponding to thelast triggering state is 0, and a state ID corresponding to the last butone triggering state is 1, and so forth.

For semi-persistent reporting, there is another implicit way ofdetermining a state ID, that is, determining a state ID according to aCSI-ReportConfigId. In particular, configuration information of eachtriggering state in first configuration information for semi-persistentreporting includes a reporting configuration identification (i.e., aCSI-ReportConfigId), and thus the CSI-ReportConfigId may be directlyused as a state ID to distinguish different triggering states.

By the approach 2, the terminal device can determine, based on acodepoint of the first information field, a first triggering state ID,and determine, based on the first triggering state ID, a correspondingfirst triggering state in the first configuration information.

Approach 3: a position of each of the at least one triggering state inthe first configuration information corresponds to a codepoint of thefirst information field.

In particular, when the first configuration information is configurationinformation for aperiodic reporting, a position of each aperiodictriggering state in the first configuration information corresponds to acodepoint of the first information field. When the first configurationinformation is configuration information for semi-persistent reporting,a position of each semi-persistent triggering state in the firstconfiguration information corresponds to a codepoint of the firstinformation field.

In an implementation, codepoints of the first information fieldcorrespond in an ascending order to triggering states from a firstposition to a last position for the triggering states in the firstconfiguration information.

In another implementation, the codepoints of the first information fieldcorrespond in a descending order to triggering states from the firstposition to the last position for the triggering states in the firstconfiguration information.

In a specific implementation, RRC signalling carrying firstconfiguration information may keep unchanged, and a triggering state isdetermined implicitly by a position of the triggering state. How todetermine the triggering state implicitly is described in combinationwith first configuration information for aperiodic reporting and firstconfiguration information for semi-persistent reporting respectively.

First configuration information for aperiodic reporting contains a list,i.e., a CSI-AperiodicTriggerStateList. A correspondence relation betweennon-zero codepoints and triggering states is determined based on theorder of positions of the triggering states in the list. For example, acodepoint ‘1’ corresponds to a triggering state at a first position, acodepoint ‘2’ corresponds to a triggering state at a second position,and so forth. Alternatively, the correspondence relation is defined in areversed order. For example, a codepoint ‘1’ corresponds to a triggeringstate at the last position, and a codepoint ‘2’ corresponds to atriggering state at the last but one position.

Similarly, first configuration information for semi-persistent reportingcontains a list, i.e., a CSI-SemiPersistentOnPUSCH-TriggerStateList. Acorrespondence relation between codepoints and triggering states isdetermined based on the order of positions of the triggering states inthe list. For example, a codepoint ‘1’ corresponds to a triggering stateat a first position, a codepoint ‘2’ corresponds to a triggering stateat a second position, and so forth. Alternatively, the correspondencerelation is defined in a reversed order. For example, a codepoint ‘1’corresponds to a triggering state at the last position, and a codepoint‘2’ corresponds to a triggering state at the last but one position.

By the approach 3, the terminal device can determine, based on acodepoint of the first information field, a first triggering state at atarget position in the first configuration information. Here, the targetposition corresponds to the codepoint of the first information field.

Approach 4: when the first configuration information is configurationinformation for semi-persistent reporting, configuration information ofeach semi-persistent triggering state in the first configurationinformation includes a reporting configuration ID, and the reportingconfiguration ID corresponds to a codepoint of the first informationfield.

In an implementation, reporting configuration IDs correspond in anascending order to codepoints of the first information field.

In another implementation, the reporting configuration IDs correspond ina descending order to the codepoints of the first information field.

In a specific implementation, RRC signalling carrying firstconfiguration information may keep unchanged, and a triggering state isdetermined implicitly by a reporting configuration ID (i.e., aCSI-ReportConfigId) corresponding to the triggering state. Inparticular, for semi-persistent reporting, each of the at least onetriggering state is configured with only one CSI-ReportConfigId (i.e.,an ID corresponding to CSI reporting configuration), and theCSI-ReportConfigId is directly used to correspond to a codepoint of theCSI request field. A correspondence relation between codepoints totriggering states is determined based on the order ofCSI-ReportConfigIds corresponding to the triggering states. For example,a codepoint ‘0’ corresponds to the minimum CSI-ReportConfigId, and acodepoint ‘1’ corresponds to the second minimum CSI-ReportConfigId.Alternatively, the correspondence relation is defined in a reversedorder. For example, a codepoint ‘0’ corresponds to the maximumCSI-ReportConfigId, and a codepoint ‘1’ corresponds to the secondmaximum CSI-ReportConfigId.

By the approach 4, the terminal device can determine, based on acodepoint of the first information field, a corresponding reportingconfiguration ID, and determine, based on the reporting configurationID, a corresponding first triggering state.

FIG. 3 illustrates a second schematic flow chart of a method fordetermining a triggering state according to some embodiments of thedisclosure. As illustrated in FIG. 3 , the method for determining atriggering state includes actions 301 and 302.

In action 301, a network device sends first configuration information toa terminal device. The first configuration information includesconfiguration information of at least one triggering state.

In embodiments of the disclosure, the network device is a base station,for example a gNB in a 5G network, and an eNB in a 4G network.

In embodiments of the disclosure, the terminal device may be any devicecapable of communicating with a network, such as a mobile phone, atablet, a vehicle-mounted terminal device and a notebook.

In embodiments of the disclosure, the first configuration information istransmitted via high-level signalling. The high-level signalling is RRCsignalling.

In embodiments of the disclosure, the first configuration informationincludes configuration information of at least one triggering state.Further, the first configuration information may be RRC signalling forconfiguring a CSI-AperiodicTriggerStateList, or RRC signalling forconfiguring a CSI-SemiPersistentOnPUSCH-TriggerStateList.

The first configuration information includes configuration informationof one or more triggering states. Generally, the first configurationinformation includes configuration information of multiple triggeringstates. The configuration information of each triggering state mayinclude but is not limited to: what information to measure, whatinformation to report, a way of information reporting, etc.

In action 302, the network device sends first control information to theterminal device. The first control information includes a firstinformation field. A codepoint of the first information field is usedfor the terminal device to determine a first triggering stateidentification (ID), and to determine, based on the first triggeringstate ID, a corresponding first triggering state in the firstconfiguration information; or the codepoint of the first informationfield is used for the terminal device to determine the first triggeringstate at a target position in the first configuration information.

In a specific implementation, the first control information may be DCI.The first information field in the first control information may becalled a CSI request field. Further, a value of the first informationfield is a codepoint of the CSI request field. For example, the firstinformation field includes 3 bits, and a value of the first informationfield may be: 000, 001, 010, 011, 100, 101, 110, or 111.

In embodiments of the disclosure, a codepoint of the first informationfield corresponds to a triggering state in the first configurationinformation. The correspondence relation may be determined in one of thefollowing approaches.

Approach 1: configuration information of each of the at least onetriggering state in the first configuration information includes asecond information field. The second information field indicates atriggering state ID of the triggering state.

In particular, when the first configuration information is configurationinformation for aperiodic reporting, configuration information of eachaperiodic triggering state includes the second information field. Thesecond information field indicates a triggering state ID of theaperiodic triggering state. When the first configuration information isconfiguration information for semi-persistent reporting, configurationinformation of each semi-persistent triggering state includes the secondinformation field. The second information field indicates a triggeringstate ID of the semi-consistent triggering state.

In a specific implementation, a triggering state identification (calleda state ID) field (i.e., the second information field) may be added toan RRC signalling carrying the first configuration information. Theimplementation of the state ID field is described in combination withfirst configuration information for aperiodic reporting and firstconfiguration information for semi-persistent reporting.

Approach 2: a position of each of the at least one triggering state inthe first configuration information corresponds to a triggering state IDof the triggering state.

In particular, when the first configuration information is configurationinformation for aperiodic reporting, a position of each aperiodictriggering state in the first configuration information corresponds to atriggering state ID of the aperiodic triggering state. When the firstconfiguration information is configuration information forsemi-persistent reporting, a position of each semi-persistent triggeringstate in the first configuration information corresponds to a triggeringstate ID of the semi-persistent triggering state.

In an implementation, triggering state IDs of triggering states in thefirst configuration information are sorted in an ascending order from afirst position to a last position for the triggering states.

In another implementation, the triggering state IDs of the triggeringstates in the first configuration information are sorted in a descendingorder from the first position to the last position for the triggeringstates.

In a specific implementation, RRC signalling carrying firstconfiguration information may keep unchanged, and a triggering state IDis determined implicitly by a position of a triggering state. How todetermine the triggering state ID implicitly is described in combinationwith first configuration information for aperiodic reporting and firstconfiguration information for semi-persistent reporting respectively.

The first configuration information for aperiodic reporting contains alist, which is a CSI-AperiodicTriggerStateList, and a state IDcorresponding to a triggering state may be determined according to aposition of the triggering state in the first configuration information(i.e., the position in the RRC signalling). For example, a state IDcorresponding to a first triggering state is 0, and a state IDcorresponding to a second triggering state is 1, and so forth.Alternatively, state IDs are sorted in a reversed order. For example, astate ID corresponding to the last triggering state is 0, and a state IDcorresponding to the last but one triggering state is 1, and so forth.

Similarly, the first configuration information for semi-persistentreporting contains a list, i.e., aCSI-SemiPersistentOnPUSCH-TriggerStateList, and a state ID correspondingto a triggering state may be determined according to a position of thetriggering state in the first configuration information (i.e., theposition in the RRC signalling). For example, a state ID correspondingto a first triggering state is 0, and a state ID corresponding to asecond triggering state is 1, and so forth. Alternatively, state IDs aresorted in a reversed order. For example, a state ID corresponding to thelast triggering state is 0, and a state ID corresponding to the last butone triggering state is 1, and so forth.

For semi-persistent reporting, there is another implicit way ofdetermining a state ID, that is, determining a state ID according to aCSI-ReportConfigId. In particular, configuration information of eachtriggering state in first configuration information for semi-persistentreporting includes a reporting configuration identification (i.e., aCSI-ReportConfigId), and thus the CSI-ReportConfigId may be directlyused as a state ID to distinguish different triggering states.

Approach 3: a position of each of the at least one triggering state inthe first configuration information corresponds to a codepoint of thefirst information field.

In particular, when the first configuration information is configurationinformation for aperiodic reporting, a position of each aperiodictriggering state in the first configuration information corresponds to acodepoint of the first information field. When the first configurationinformation is configuration information for semi-persistent reporting,a position of each semi-persistent triggering state in the firstconfiguration information corresponds to a codepoint of the firstinformation field.

In an implementation, codepoints of the first information fieldcorrespond in an ascending order to triggering states from a firstposition to a last position for the triggering states in the firstconfiguration information.

In another implementation, the codepoints of the first information fieldcorrespond in a descending order to triggering states from the firstposition to the last position for the triggering states in the firstconfiguration information.

In a specific implementation, RRC signalling carrying firstconfiguration information may keep unchanged, and a triggering state isdetermined implicitly by a position of the triggering state. How todetermine the triggering state implicitly is described in combinationwith first configuration information for aperiodic reporting and firstconfiguration information for semi-persistent reporting respectively.

First configuration information for aperiodic reporting contains a list,which is a CSI-AperiodicTriggerStateList. A correspondence relationbetween non-zero codepoints and triggering states is determined based onthe order of positions of the triggering states in the list. Forexample, a codepoint ‘1’ corresponds to a triggering state at a firstposition, a codepoint ‘2’ corresponds to a triggering state at a secondposition, and so forth. Alternatively, the correspondence relation isdefined in a reversed order. For example, a codepoint ‘1’ corresponds toa triggering state at the last position, and a codepoint ‘2’ correspondsto a triggering state at the last but one position.

Similarly, first configuration information for semi-persistent reportingcontains a list, i.e., a CSI-SemiPersistentOnPUSCH-TriggerStateList. Acorrespondence relation between codepoints and triggering states isdetermined based on the order of positions of the triggering states inthe list. For example, a codepoint ‘1’ corresponds to a triggering stateat a first position, a codepoint ‘2’ corresponds to a triggering stateat a second position, and so forth. Alternatively, the correspondencerelation is defined in a reversed order. For example, a codepoint ‘1’corresponds to a triggering state at the last position, and a codepoint‘2’ corresponds to a triggering state at the last but one position.

Approach 4: when the first configuration information is configurationinformation for semi-persistent reporting, configuration information ofeach semi-persistent triggering state in the first configurationinformation includes a reporting configuration ID, and the reportingconfiguration ID corresponds to a codepoint of the first informationfield.

In an implementation, reporting configuration IDs correspond in anascending order to codepoints of the first information field.

In another implementation, the reporting configuration IDs correspond ina descending order to the codepoints of the first information field.

In a specific implementation, RRC signalling carrying firstconfiguration information may keep unchanged, and a triggering state isdetermined implicitly by a reporting configuration ID (i.e., aCSI-ReportConfigId) corresponding to the triggering state. Inparticular, for semi-persistent reporting, each of the at least onetriggering state is configured with only one CSI-ReportConfigId (i.e.,an ID corresponding to CSI reporting configuration), and theCSI-ReportConfigId directly corresponds to a codepoint of the CSIrequest field. A correspondence relation between codepoints andtriggering states is determined based on the order ofCSI-ReportConfigIds corresponding to the triggering states. For example,a codepoint ‘0’ corresponds to a minimum CSI-ReportConfigId, and acodepoint ‘1’ corresponds to a second minimum CSI-ReportConfigId.Alternatively, the correspondence relation is defined in a reversedorder. For example, a codepoint ‘0’ corresponds to a maximumCSI-ReportConfigId, and a codepoint ‘1’ corresponds to a second maximumCSI-ReportConfigId.

FIG. 4 illustrates a first schematic diagram of structural compositionof a device for determining a triggering state according to someembodiments of the disclosure. As illustrated in FIG. 4 , the deviceincludes a first receiving unit 401, a second receiving unit 402 and adetermination unit 403.

The first receiving unit 401 is configured to receive firstconfiguration information from a network device. The first configurationinformation includes configuration information of at least onetriggering state.

The second receiving unit 402 is configured to receive first controlinformation from the network device. The first control informationincludes a first information field.

The determination unit 402 is configured to determine, based on acodepoint of the first information field, a first triggering stateidentification (ID), and determine, based on the first triggering stateID, a corresponding first triggering state in the first configurationinformation. Or, the determination unit 402 is configured to determine,based on the codepoint of the first information field, the firsttriggering state at a target position in the first configurationinformation.

In an implementation, configuration information of each of the at leastone triggering state in the first configuration information includes asecond information field. The second information field indicates atriggering state ID of the triggering state.

In an implementation, when the first configuration information isconfiguration information for aperiodic reporting, configurationinformation of each aperiodic triggering state includes the secondinformation field. The second information field indicates a triggeringstate ID of the aperiodic triggering state.

Or, when the first configuration information is configurationinformation for semi-persistent reporting, configuration information ofeach semi-persistent triggering state includes the second informationfield. The second information field indicates a triggering state ID ofthe semi-consistent triggering state.

In an implementation, a position of each of the at least one triggeringstate in the first configuration information corresponds to a triggeringstate ID of the triggering state.

In an implementation, when the first configuration information isconfiguration information for aperiodic reporting, a position of eachaperiodic triggering state in the first configuration informationcorresponds to a triggering state ID of the aperiodic triggering state.

Or, when the first configuration information is configurationinformation for semi-persistent reporting, a position of eachsemi-persistent triggering state in the first configuration informationcorresponds to a triggering state ID of the semi-persistent triggeringstate.

In an implementation, a position of each of the at least one triggeringstate in the first configuration information corresponds to a triggeringstate ID of the triggering state, in an event that: triggering state IDsof triggering states in the first configuration information are sortedin an ascending order from a first position to a last position for thetriggering states; or the triggering state IDs of the triggering statesin the first configuration information are sorted in a descending orderfrom the first position to the last position for the triggering states.

In an implementation, a position of each of the at least one triggeringstate in the first configuration information corresponds to a codepointof the first information field.

In an implementation, when the first configuration information isconfiguration information for aperiodic reporting, a position of eachaperiodic triggering state in the first configuration informationcorresponds to a codepoint of the first information field.

Or, when the first configuration information is configurationinformation for semi-persistent reporting, a position of eachsemi-persistent triggering state in the first configuration informationcorresponds to a codepoint of the first information field.

In an implementation, a position of each of the at least one triggeringstate in the first configuration information corresponds to a codepointof the first information field in an event that: codepoints of the firstinformation field correspond in an ascending order to triggering statesfrom a first position to a last position for the triggering states inthe first configuration information; or the codepoints of the firstinformation field correspond in a descending order to triggering statesfrom the first position to the last position for the triggering statesin the first configuration information.

In an implementation, when the first configuration information isconfiguration information for semi-persistent reporting, configurationinformation of each semi-persistent triggering state in the firstconfiguration information includes a reporting configuration ID, and thereporting configuration ID corresponds to a codepoint of the firstinformation field.

In an implementation, the reporting configuration informationcorresponds to a codepoint of the first information field in an eventthat: reporting configuration IDs correspond in an ascending order tocodepoints of the first information field; or the reportingconfiguration IDs correspond in a descending order to the codepoints ofthe first information field.

Those skilled in the art should understand that description related tothe device for determining a triggering state according to embodimentsof the disclosure can be comprehend with reference to the descriptionrelated to the method for determining a triggering state according toembodiments of the disclosure.

FIG. 5 illustrates a second schematic diagram of structural compositionof a device for determining a triggering state according to someembodiments of the disclosure. As illustrated in FIG. 5 , the deviceincludes a first sending unit 501 and a second sending unit 502.

The first sending unit 501 is configured to send first configurationinformation to a terminal device. The first configuration informationincludes configuration information of at least one triggering state.

The second sending unit 502 is configured to send first controlinformation to the terminal device. The first control informationincludes a first information field.

A codepoint of the first information field is used for the terminaldevice to determine a first triggering state identification (ID), and todetermine, based on the first triggering state ID, a corresponding firsttriggering state in the first configuration information; or thecodepoint of the first information field is used for the terminal deviceto determine the first triggering state at a target position in thefirst configuration information.

In an implementation, configuration information of each of the at leastone triggering state in the first configuration information includes asecond information field. The second information field indicates atriggering state ID of the triggering state.

In an implementation, when the first configuration information isconfiguration information for aperiodic reporting, configurationinformation of each aperiodic triggering state includes the secondinformation field. The second information field indicates a triggeringstate ID of the aperiodic triggering state; or when the firstconfiguration information is configuration information forsemi-persistent reporting, configuration information of eachsemi-persistent triggering state includes the second information field.The second information field indicates a triggering state ID of thesemi-consistent triggering state.

In an implementation, a position of each of the at least one triggeringstate in the first configuration information corresponds to a triggeringstate ID of the triggering state.

In an implementation, when the first configuration information isconfiguration information for aperiodic reporting, a position of eachaperiodic triggering state in the first configuration informationcorresponds to a triggering state ID of the aperiodic triggering state.

Or, when the first configuration information is configurationinformation for semi-persistent reporting, a position of eachsemi-persistent triggering state in the first configuration informationcorresponds to a triggering state ID of the semi-persistent triggeringstate.

In an implementation, a position of each of the at least one triggeringstate in the first configuration information corresponds to a triggeringstate ID of the triggering state in an event that: triggering state IDsof triggering states in the first configuration information are sortedin an ascending order from a first position to a last position for thetriggering states; or the triggering state IDs of the triggering statesin the first configuration information are sorted in a descending orderfrom the first position to the last position for the triggering states.

In an implementation, a position of each of the at least one triggeringstate in the first configuration information corresponds to a codepointof the first information field.

In an implementation, when the first configuration information isconfiguration information for aperiodic reporting, a position of eachaperiodic triggering state in the first configuration informationcorresponds to a codepoint of the first information field.

Or, when the first configuration information is configurationinformation for semi-persistent reporting, a position of eachsemi-persistent triggering state in the first configuration informationcorresponds to a codepoint of the first information field.

In an implementation, a position of each of the at least one triggeringstate in the first configuration information corresponds to a codepointof the first information field in an event that: codepoints of the firstinformation field correspond in an ascending order to triggering statesfrom a first position to a last position for the triggering states inthe first configuration information; or the codepoints of the firstinformation field correspond in a descending order to triggering statesfrom the first position to the last position for the triggering statesin the first configuration information.

In an implementation, when the first configuration information isconfiguration information for semi-persistent reporting, configurationinformation of each semi-persistent triggering state in the firstconfiguration information includes a reporting configuration ID, and thereporting configuration ID corresponds to a codepoint of the firstinformation field.

In an implementation, the reporting configuration informationcorresponds to a codepoint of the first information field in an eventthat: reporting configuration IDs correspond in an ascending order tocodepoints of the first information field; or the reportingconfiguration IDs correspond in a descending order to the codepoints ofthe first information field.

Those skilled in the art should understand that description related tothe device for determining a triggering state according to embodimentsof the disclosure can be comprehend with reference to the descriptionrelated to the method for determining a triggering state according toembodiments of the disclosure.

FIG. 6 illustrates a schematic structural diagram of a communicationdevice 600 according to some embodiments of the disclosure. Thecommunication device may be a terminal device or a network device. Thecommunication device 600 as illustrated in FIG. 6 includes a processor610. The processor 610 can call and run a computer program from amemory, to implement the method according to the embodiments of thedisclosure.

As illustrated in FIG. 6 , the communication device 600 may furtherinclude a memory 620. The processor 610 can call and run a computerprogram from the memory 620, to implement the method according to theembodiments of the disclosure.

The memory 620 may be a separate device independent from the processor610, or may be integrated into the processor 610.

As illustrated in FIG. 6 , the communication device 600 may furtherinclude a transceiver 630. The processor 610 may control the transceiver630 to communicate with another device, particularly, sendinginformation or data to another device or receiving information or datafrom another device.

The transceiver 630 may include a transmitter and a receiver. Thetransceiver 630 may further include one or more antennas.

The communication device 600 may specifically be the network deviceaccording to the embodiments of the disclosure. The communication device600 may implement corresponding processes implemented by the networkdevice in each method according to the embodiments of the disclosure,which will not be described here for simplicity.

The communication device 600 may specifically be a mobileterminal/terminal device according to the embodiments of the disclosure.The communication device 600 may implement corresponding processesimplemented by the mobile terminal/terminal device in each methodaccording to the embodiments of the disclosure, which will not bedescribed here for simplicity.

FIG. 7 illustrates a schematic structural diagram of a chip according tosome embodiments of the disclosure. The chip as illustrated in FIG. 7includes a processor 710. The processor 710 can call and run a computerprogram from the memory, to implement the method according to theembodiments of the disclosure.

As illustrated in FIG. 7 , the chip 700 may further include a memory720. The processor 710 can call and run a computer program from thememory 720, to implement the method according to the embodiments of thedisclosure.

The memory 720 may be a separate device independent from the processor710, or may be integrated into the processor 710.

The chip 700 may further include an input interface 730. The processor710 may control the input interface 730 to communicate with anotherdevice or chip, particularly, may acquire information or data fromanother device or chip.

The chip 700 may further include an output interface 740. The processor710 may control the output interface 740 to communicate with anotherdevice or chip, particularly, may output information or data to anotherdevice or chip.

The chip may be applied to the network device according to theembodiments of the disclosure. The chip may implement correspondingprocesses implemented by the network device in each method according tothe embodiments of the disclosure, which will not be described here forsimplicity.

The chip may be applied to a mobile terminal/terminal device accordingto the embodiments of the disclosure. The chip may implementcorresponding processes implemented by the mobile terminal/terminaldevice in each method according to the embodiments of the disclosure,which will not be described here for simplicity.

It is to be understood that the chip described to the embodiments of thedisclosure may also be called a system-level chip, a system chip, a chipsystem, a system on chip or the like.

FIG. 8 illustrates a schematic block diagram of a communication system900 provided according to some embodiments of the disclosure. Asillustrated in FIG. 8 , the communication system 900 includes a terminaldevice 910 and a network device 920.

The terminal device 910 may be used for implementing correspondingfunctions implemented by a terminal device in the above method, and thenetwork device 920 may be used for implementing corresponding functionsimplemented by a network device in the above method, which will not bedescribed here for simplicity.

It is to be understood that the processor in the embodiments of thedisclosure may be an integrated circuit chip, and has a signalprocessing capability. During implementation, each of the methodembodiment above may be implemented by an integrated logic circuit ofhardware or instructions in a software form in the processor. Theprocessor above may be a general-purpose processor, a digital signalprocessor (DSP), an application specific integrated circuit (ASIC), afield programmable gate array (FPGA) or other programmable logicdevices, transistor logic devices, discrete hardware components, etc.The processor can realize or execute the method, steps and logical blockdiagrams disclosed in the embodiments of the disclosure. Thegeneral-purpose processor may be a microprocessor, or the processor maybe any ordinary processor. The actions of the method disclosed inconjunction with the embodiments of the disclosure may be directlyembodied to be accomplished by a hardware decoding processor, or by acombination of hardware and software modules in the decoding processor.The software module may be located in a storage medium mature in therelated art, such as a random memory, a flash, a read-only memory, aprogrammable read-only memory or an electrically erasable programmableread-only memory, and a register. The storage medium is a memory, andthe processor reads information in the memory and completes steps of theabove method in combination with hardware.

It is to be understood that, in the embodiments of the disclosure, thememory may be a volatile memory or a non-volatile memory, or includesboth a volatile and non-volatile memories. The non-volatile memory maybe a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM(EPROM), an electrically EPROM (EEPROM) or a flash. The volatile memorymay be a random access memory (RAM), and is used as an external cache.By exemplary but not limiting description, many types of RAMs areavailable, a static RAM (SRAM), a dynamic RAM (DRAM), a synchronous DRAM(SDRAM), a double data rate SDRAM (DDR SDRAM), an enhanced SDRAM(ESDRAM), a synchronous link DRAM (SLDRAM) and a direct rambus RAM (DRRAM). It is to be noted that, the memory in the system and methoddescribed herein are intended to include but are not limited to theseand any other suitable type of memories.

It is to be understood that the description of the memory is exemplarybut not limiting. By way of example, the memory in the embodiments ofthe disclosure may also be a static RAM (SRAM), a dynamic RAM (DRAM), asynchronous DRAM (SDRAM), a double data rate SDRAM (DDR SDRAM), anenhanced SDRAM (ESDRAM), a synchronous link DRAM (SLDRAM) and a directrambus RAM (DR RAM). That is to say, the memory in the embodiments ofthe disclosure are intended to include but are not limited to these andany other suitable type of memories.

A computer-readable storage medium for storing a computer program isfurther provided in embodiments of the disclosure.

The computer-readable storage medium may be applied to the networkdevice according to the embodiments of the disclosure. Thecomputer-readable storage medium may implement corresponding processesimplemented by the network device in each method according to theembodiments of the disclosure, which will not be described here forsimplicity.

The computer-readable storage medium may be applied to a mobileterminal/terminal device according to the embodiments of the disclosure.The computer program enables a computer to implement correspondingprocesses implemented by the mobile terminal/terminal device in eachmethod according to the embodiments of the disclosure, which will not bedescribed here for simplicity.

A computer program product including computer program instructions isfurther provided in embodiments of the disclosure.

The computer program product may be applied to the network deviceaccording to the embodiments of the disclosure. The computer programinstructions enable a computer implement corresponding processesimplemented by the network device in each method according to theembodiments of the disclosure, which will not be described here forsimplicity.

The computer program product may be applied to the mobileterminal/terminal device according to the embodiments of the disclosure.The computer program instructions enable a computer to implementcorresponding processes implemented by the mobile terminal/terminaldevice in each method according to the embodiments of the disclosure,which will not be described here for simplicity.

A computer program is further provided in embodiments of the disclosure.

The computer program may be applied to the network device according tothe embodiments of the disclosure. The computer program, when running ona computer, enables the computer to implement corresponding processesimplemented by the network device in each method according to theembodiments of the disclosure, which will not be described here forsimplicity.

The computer program may be applied to the mobile terminal/terminaldevice according to the embodiments of the disclosure. The computerprogram, when running on a computer, enables the computer to implementcorresponding processes implemented by the mobile terminal/terminaldevice in each method according to the embodiments of the disclosure,which will not be described here for simplicity.

It may be appreciated by those of ordinary skilled in the art that unitsand algorithm steps in each example described in combination with theembodiments disclosed herein may be implemented by electronic hardware,or a combination of computer software and electronic hardware. Whetherthese functions are implemented in the form of hardware or softwaredepends on specific application of the technical solution and constraintconditions in design. The professionals may implement the describedfunctions in different ways for each specific application, but suchimplementation should not be construed beyond the scope of thedisclosure.

Those skilled in the art may clearly understand that the particularoperation of the system, device and units described above may refer tothe corresponding operations in the method embodiment above, which willnot be described here, for convenience and simplicity of description.

In the embodiments provided, it is to be understood that the disclosedsystem, device and method may be embodied in other ways. For example,the device embodiment described above is merely exemplarily. Forexample, the division of units is merely division of logical functions,and the units may be divided in other ways in practical implementation.For example, multiple units or components may be combined or integratedinto another system, or some features may be neglected or not executed.Additionally, the displayed or discussed mutual coupling or directcoupling or communication connection may be implemented through someinterfaces, and indirect coupling or communication connections betweendevices or units may be electrical, mechanical or other forms.

Units described as separate parts therein may or may not be physicallyseparated, and parts displayed as units may or may not be physicalunits, and namely may be located in the same place or may also bedistributed to multiple network units. Some or all of the units may beselected according to a practical requirement to achieve the purpose ofthe solutions of the embodiments.

Furthermore, in the embodiments of the disclosure, various functionalunits may be integrated into a processing unit, or each unit may existalone physically, or two or more units may be integrated into one unit.

When being implemented in form of software functional unit and sold orused as an independent product, the functions may be stored in acomputer-readable memory. Based on such an understanding, the technicalsolutions of the disclosure substantially or parts making contributionsto the related art or all or part of the technical solutions may beembodied in form of software product, and the computer software productis stored in a memory, including a plurality of instructions configuredto enable a computer device (which may be a personal computer, a server,network device or the like) to execute all or part of the actions of themethod in each embodiment of the disclosure. The storage medium aboveincludes various media capable of storing program codes such as a Udisk, a read-only memory (ROM), a random access memory (RAM), a mobilehard disk, a magnetic disk or an optical disk.

The above are only detailed description of the disclosure, but the scopeof protection of the disclosure is not limited to this. Changes orreplacements that would come up to those skilled in the art should fallwithin the coverage of the disclosure. Therefore, the scope ofprotection of the disclosure should be defined by the claims.

The invention claimed is:
 1. A method for determining a triggeringstate, comprising: sending, by a network device, first configurationinformation to a terminal device, wherein the first configurationinformation is radio resource control (RRC) signalling for configuring aCSI-SemiPersistentOnPUSCH-TriggerStateList, and the first configurationinformation comprises configuration information of at least onetriggering state; and sending, by the network device, downlink controlinformation (DCI) to the terminal device, wherein the DCI comprises achannel state information (CSI) request field, wherein a codepoint ofthe CSI request field is used for the terminal device to determine thefirst triggering state at a target position in the first configurationinformation, and wherein a position of each of the at least onetriggering state in the first configuration information corresponds to acodepoint of the CSI request field, a starting codepoint of the CSIrequest field corresponding to a triggering state is 0, and codepointsof the CSI request field correspond in an ascending order to triggeringstates from a first position to a last position for the triggeringstates in the first configuration information.
 2. The method accordingto claim 1, wherein the configuration information of each of the atleast one triggering state in the first configuration informationcomprises a second information field, and the second information fieldindicates a triggering state ID of the triggering state.
 3. The methodaccording to claim 2, wherein the first configuration informationfurther comprises the second information field, wherein the secondinformation field indicates a triggering state ID of the semi-consistenttriggering state.
 4. A network device, comprising: a processor, atransceiver and a memory for storing a computer program, wherein theprocessor is configured to call and execute the computer program storedin the memory, to: send first configuration information to a terminaldevice, wherein the first configuration information is radio resourcecontrol (RRC) signalling for configuring aCSI-SemiPersistentOnPUSCH-TriggerStateList, and the first configurationinformation comprises configuration information of at least onetriggering state; and send downlink control information (DCI) to theterminal device, wherein the DCI comprises a channel state information(CSI) request field, wherein a codepoint of the CSI request field isused for the terminal device to determine the first triggering state ata target position in the first configuration information, and wherein aposition of each of the at least one triggering state in the firstconfiguration information corresponds to a codepoint of the CSI requestfield, a starting codepoint of the CSI request field corresponding to atriggering state is 0, and codepoints of the CSI request fieldcorrespond in an ascending order to triggering states from a firstposition to a last position for the triggering states in the firstconfiguration information.
 5. The network device according to claim 4,wherein the configuration information of each of the at least onetriggering state in the first configuration information comprises asecond information field, wherein the second information field indicatesa triggering state ID of the triggering state.
 6. The network deviceaccording to claim 5, wherein the first configuration informationfurther comprises the second information field, wherein the secondinformation field indicates a triggering state ID of the semi-consistenttriggering state.